got rid of the error check because we don't actually care what the config digest is and asserting an error would actually cause you to transmit more rounds

the changes look fine - but why is LatestRoundRequested implemented in two places? it seems very easy to make changes in one place but forget to make changes in the other

originally i think it was to have a cached response and save time. libocr uses the transmissions_cache to satisfy the ContractTransmitter interface.

now that we know we can always return 0 I think we don't need the underlying method. i'll edit that out

oh wait, actually the Reader needs to implement it because it must conform to the interface was well

i removed the need to query the chain and to use the lock

I guess my suggestion is - instead of having zero values implemented twice, why not just call c.reader.LatestRoundRequested and add a note saying that this will always return zero values?

that way you only have hard-coded values in one place rather than two places

oh i see what you mean. will do 👍